-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make sure current task build id works with queries / caching #665
Make sure current task build id works with queries / caching #665
Conversation
1312603
to
db8745d
Compare
@@ -420,9 +418,15 @@ impl WorkflowMachines { | |||
Some(workflow_activation_job::Variant::QueryWorkflow(_)) | |||
) | |||
}); | |||
let is_replaying = self.replaying || all_query; | |||
let build_id_for_current_task = if is_replaying { | |||
self.current_wft_build_id.clone().unwrap_or_default() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does core need the same logic as Go to check for an empty build ID?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The lookahead works a bit differently and avoids this problem - I actually ended up changing the Go one to be a bit simpler and more similar in my last fix too.
@@ -420,9 +418,15 @@ impl WorkflowMachines { | |||
Some(workflow_activation_job::Variant::QueryWorkflow(_)) | |||
) | |||
}); | |||
let is_replaying = self.replaying || all_query; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Aren't queries considered replaying anyway?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not until this point, that's where it happens
What was changed
Made the current task build id sent on activations consistent with what I just did in Go / Java.
Why?
Part of temporalio/features#253
Checklist
Closes
How was this tested: